New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate another usage of utiltrace to component base tracing #113698
Migrate another usage of utiltrace to component base tracing #113698
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
/assign @sttts |
/priority important-soon |
very localized change. one file. already has approval from @logicalhan. I am comfortable getting this in. /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dashpole, dims, logicalhan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/sig instrumentation
/kind feature
What this PR does / why we need it:
Follow-up to #113172. I had missed one usage of utiltracing. This change keeps existing log-based "tracing" in-place without changes. It also results in OpenTelemetry spans being created for the tracing.Start calls if APIServerTracing is enabled.
Which issue(s) this PR fixes:
#113170
Does this PR introduce a user-facing change?
/assign @logicalhan